Fix MSA reading in predict.py #538
Conversation
|
Hi @alex-hh! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
facebook-github-bot
added
the
CLA Signed
This is an attempt to fix the error encountered when running predict.py using the MSA Transformer on the example data provided in examples/variant-prediction/data (#458)
The reason for the current error appears to be that the example MSA has an EVMutation-specific usage of lower-case columns to signify low-coverage (nonfocus) columns and not insertions. In this case the desired behaviour is presumably to coerce such columns to upper-case for scoring. This was the original behaviour of predict.py, before the PR #230, which seems to be intended to support the standard usage of lower-case residues to designate insertions in user-supplied a2m/a3m files and inadvertently breaks the example.
This PR supports both options via the lowercase-type flag. The default treats the lower-case columns as EVMutation style nonfocus (i.e. low coverage) columns for compatibility with the example MSA.